How do you want a reputation as an excellent, outstanding developer?

 How do you want a reputation as an excellent, outstanding developer?

 How do you want a reputation as an excellent, outstanding developer?

Are other developers on your team looking for you?

Need to be seen as the “star coder” of your organization?

If you want to be the kind of coder who legitimately demands this honor from your colleagues ... there are a few things that need to be above and beyond the basic skills of your software developer.

Some of these issues are social and some are technical.

For now, let's talk about the technical aspects. Meaning, the kind of code you write. And how it affects or influences others in your group.

Here are some of the reasons:

1) Develop strong and reliable code

As part of a team, you are writing the code that other developers are using and of course it should be created.

When they do, do they think your code is fragile? What breaks easily when something goes beyond normal limits? For example, what if the program is fed 10 times more data than normal?

Or do they make it strong, reliable ... as strong as a rock?

Over time, people who reuse your code will develop feelings about your code - positive or negative.

And being human they can’t help connecting this feeling to you.

2) Maintainable code

Requirements change over time. Or better understood than before.

And your teammates need to change the code to add it. With your * code.

Do you tend to write code in a way that makes it easier? At least, straight?

Or your code is often difficult to modify in the event of an unknown future change - to the point where they sometimes have to drop your code and start over?

3) Managing explosive data inputs with arrest

We are in the big data age. And it’s just getting bigger.

This trend will not change.

So when you write software - functions, classes, programs - you write it to handle more data than you need?

Does your code create huge data structures that run the operating system on a disk page? What is the use of a program?

Or blocking the user's interface because it is processing a collection with a memory constraint ... when it can respond to a component at once?

Programmers are naturally impatient. When something wastes our time, we “feel” its pain more than others.

Again: whatever your code makes your fellow developers feel, they can't help you instead.

4) Inspirational

Does your code show other developers a better way?

Does this prove that somehow they can clearly understand and apply, how to enhance skills on their own craft? Do you just read the code?

...

These are just some of the factors that will help you to increase your reputation among your peers.

I'm not saying this should be the primary goal of your career. But it doesn't matter. And it does every positive thing you want to make easier to perform.